Documentation
LiveSPInstallation Operating GuideDownload PDF
Monitoring : Data Collection : Check 3 – SNMP data collection works fine
Check 3 – SNMP data collection works fine
Process
API endpoint: /api/v1/collect/status//SNMP
CUSTOMER_ID: identifier of the customer tenant from provisioning
Expected: status value should equal to HEALTHY
Severity: High
Services involved in the SNMP collection chain are:
livesp_sinemapro-proxy
livesp_sinemapro-slave
livesp_esus-collector
livesp_esus-farcaster*
Support action
1. Are all these services up and running?
Source: See Services
If yes: Fix this first
2. Was there a recent degradation and when did it start?
Source: ELK dashboard SNMP Analysis (last 4, 12 and 48 hours)
Expected observation on graphs:
Good stability of the number of realms (total, and per Farcaster node)
Relative stability of the number of lines in bridge
No alert regarding CPU load, memory load and disk space
If yes: Capture snapshots, summarize observations
3. Is SNMP bridge collection working fine for the customer?
Source: Run command checkSNMPCollectedFor
Expected outputs: JSON element with a lineCount property greater than 0
{
  'clientId':'2314459',
  'date':'2020-03-28-01-00',
  'lineCount':7,
  'hostname':'snmpcollector3',
  'ipaddress':'10.156.129.225',
  'bridgePath':'/data/files/bridge/snmp/interface/data-2020-03-28-01-00-00'
}
If no (lineCount = 0): The source of the problem is on SNMP packet collection side
Select 1 or 2 CPEs with wanLinks for this customer (LiveSP inventory screen)
Any error or warn in sinemapro-slave logs filtered on this CPE IP address?
If yes (lineCount > 0): The source of the problem is on Memdex collection side.
Any error in esus-collector logs?
Example
Request URL: https://mylivesp.com/api/v1/collect/status/7/SNMP
Response JSON content:
{
  "id": "snmp",
  "name": "SNMP",
  "type": "TECHNOLOGY",
  "status": "HEALTHY",
  "message": "Collect is healthy for technology SNMP"
}